home *** CD-ROM | disk | FTP | other *** search
- Path: news.compuserve.com!newsmaster
- From: 100754.2730@compuserve.com (Martin Aupperle)
- Newsgroups: comp.lang.c++
- Subject: Re: Constructor Exceptions
- Date: Mon, 08 Jan 1996 08:08:13 GMT
- Organization: CompuServe Incorporated
- Message-ID: <4cqjps$337@dub-news-svc-1.compuserve.com>
- References: <4bud9g$pv5@oxy.rust.net> <4cbhcl$kst@dawn.mmm.com> <4ce68n$8u4@sundog.tiac.net> <4ch1c3$bsm@oxy.rust.net>
- NNTP-Posting-Host: ad35-142.compuserve.com
- X-Newsreader: Forte Free Agent v0.56
-
- pgunn@mail.cbf.com (Paul Gunn) wrote:
-
-
- >Here is an excerpt from the Visual C++ 2.1 documentation. It seems to
- >indicate that 'this' will not be cleaned up.
-
- [snip]
-
- Visual C++ 2.1 does not implement exception handling as part of the
- language. Instead, you use macros that translate into a simulation. If
- I remember right, constructors are not the only area where that
- mechanism does not work correctly. Stack unwinding and destroying
- already created subobjects do not work either. Also, you have to
- derive your exception classes from a certain base class.
- So MSVC's exceptions can be used if you are careful and are aware of
- the drawbacks.
-
- Why don't you use MSVC 4.0 or Borland? They implement exceptions
- correctly.
-
-
-
-
-
- -----------------------------------
- Signatures are a waste of bandwidth
- -----------------------------------
-
-